What are the most popular causes of comment errors when running the k with Mach? Gotten a few of them lately and the last one happened while jogging where it kept going
B
Group: DynoMotion
Message: 8259
From: Tom Kerekes
Date: 9/4/2013
Subject: Re: Comm error problems
Hi Bill.
Communication errors basically come in two types: One is when there is a power glitch which causes KFLOP to re-boot. The other is when something causes Windows to disconnect the USB connection. If you can re-establish communication (without power cycling KFLOP) and check if KFLOP is still configured with your settings then you know that KFLOP did not re-boot. Are you using an external +5V supply for KFLOP? Or USB powered?
Regards
TK
Group: DynoMotion
Message: 8261
From: Wcarrothers Yahoo
Date: 9/4/2013
Subject: Re: Comm error problems
Hello
It is external powered.
It would happen on occasion when the machine was at my home. Just moved it to my building and happens more. Course the power source is different
When it happens All I do is hit the estop button on the Mach screen and continue. So I don't think it is rebooting in this case. So then it is more the computer or USB port
B
On Sep 4, 2013, at 5:11 PM, Tom Kerekes <tk@...> wrote:
Hi Bill.
Communication errors basically come in two types: One is when there is a power glitch which causes KFLOP to re-boot. The other is when something causes Windows to disconnect the USB connection. If you can re-establish communication (without power cycling KFLOP) and check if KFLOP is still configured with your settings then you know that KFLOP did not re-boot. Are you using an external +5V supply for KFLOP? Or USB powered?
Regards
TK
Group: DynoMotion
Message: 8262
From: Wcarrothers Yahoo
Date: 9/4/2013
Subject: Re: Comm error problems
Also. Not sure if it could be a power glitch on my setup as on the 5 and 12v lines to the electrics and k I have several large caps after the power supply. Enough to keep the k powered for maybe 20-30 seconds if the power supply were to glitch
So must be the pc?
On Sep 4, 2013, at 5:11 PM, Tom Kerekes <tk@...> wrote:
Hi Bill.
Communication errors basically come in two types: One is when there is a power glitch which causes KFLOP to re-boot. The other is when something causes Windows to disconnect the USB connection. If you can re-establish communication (without power cycling KFLOP) and check if KFLOP is still configured with your settings then you know that KFLOP did not re-boot. Are you using an external +5V supply for KFLOP? Or USB powered?
Regards
TK
Group: DynoMotion
Message: 8264
From: Tom Kerekes
Date: 9/4/2013
Subject: Re: Comm error problems
Hi Bill,
Did you mean to say the RESET button. The RESET button re-initializes everything after a re-boot. So if you are doing that it doesn't prove anything.
Regards
TK
Group: DynoMotion
Message: 8265
From: Wcarrothers Yahoo
Date: 9/4/2013
Subject: Re: Comm error problems
Yes the reset button on the Mach screen. I don't loose any position so was thinking it could not be a reboot
Other times it stops on gcode lines which are retracts for axis a and Z Those cases are different in that while Reset is blinking the a azis creeps in he up direction slow (I don't have the zero offset for the analog set in that drive like I do in z) but creeps till I hit reset at which point the actual position updates
Anyway something I'm used to but if a faster computer with better USB would cure I might try. Remember I run xp on older pentium 4 machines
Looking forward to getting my other k and snap amps up. But probably several months off from that
B
On Sep 4, 2013, at 6:45 PM, Tom Kerekes <tk@...> wrote:
Hi Bill,
Did you mean to say the RESET button. The RESET button re-initializes everything after a re-boot. So if you are doing that it doesn't prove anything.
Regards
TK
Group: DynoMotion
Message: 8266
From: Tom Kerekes
Date: 9/4/2013
Subject: Re: Comm error problems
Hi Bill,
Good observation. If the encoder position is not lost then KFLOP could not be rebooting.
That would indicate something in the USB causing Windows
to disconnect. I can't think of an easy way to pin it down without changing things and testing. Older PC should not be a problem.
Regards
TK
Group: DynoMotion
Message: 8267
From: Wcarrothers Yahoo
Date: 9/4/2013
Subject: Re: Comm error problems
Ok. Will continue to watch it. Since it does not loose position I figured it was a connection or noise issue or was triggering the follow error. Thinking it mostly happens on a rapid retract of the heavy axis. But I slowed the acceleration on them and still does it just about as much. Will sort it out some day.
Most of the time it is just a click of the button and continue. Only a few times I've gotten the firmware miss match screen in which case I had to reboot the k and restart Mach re zero everything. But that has only happened maybe 3 times total vs the other which might interrupt running a part 5-9 times out out of 100 runs
B
On Sep 4, 2013, at 7:49 PM, Tom Kerekes <tk@...> wrote:
Hi Bill,
Good observation. If the encoder position is not lost then KFLOP could not be rebooting.
That would indicate something in the USB causing Windows
to disconnect. I can't think of an easy way to pin it down without changing things and testing. Older PC should not be a problem.